Skip to main content

Traffic Policies Overview

You can manage your traffic by defining traffic policies. Traffic policies provide the ability to control the distribution of the traffic between the different CDN providers for each geolocation. You can define policies based on 3 main characteristics:

  • Performance - Pick the best performing CDN provider in each geolocation.
  • Availability - Automatic failover between CDNs in case something is wrong with one of them.
  • Cost - Optimize cost by selecting priorities between CDNs and configuring commitment.

Traffic policies are geo based. The default traffic policy is automatically created when you create your service, and it includes the entire world. This policy cannot be deleted. You can configure this policy or add additional policies for specific geolocations. Geolocation can be either a country, a state, or an entire continent. When you create multiple policies, the more specific one takes precedence. For example, assume you created a policy for Europe and configured it to use CDN-A, then you created another policy for France with CDN-B. In this case the policy for France will take precedence over the policy for Europe.

Prerequisites​

Before starting to work with traffic-policies, you will need to have the following:

  • IO River Service - You can follow these steps to create a service.
  • CDN Account - You will need at least one CDN account to be used with your service.